Systems and methods for electronically processing government sponsored benefits

ABSTRACT

Systems and methods for processing benefits include providing a graphical user interface, such as a web browser, to a benefit recipient for accessing at least account information concerning at least one benefit type. The benefits processing system may receive a request from the benefit recipient through the graphical user interface for displaying the at least account information concerning the at least one benefit type. The benefits processing system may then display the at least account information through the graphical user interface concerning the at least one benefit type.

This application claims priority under 35 U.S.C. §119 based on U.S.Provisional Application No. 60/414,645, filed Oct. 1, 2002, the completedisclosure of which is incorporated herein by reference.

FIELD OF THE INVENTION

This invention is related to data management, and more particularly to amethod and system for electronically processing government sponsoredbenefits.

BACKGROUND

Federal and state governments are responsible for protecting the welfareof its citizens. As a consequence, programs have been established thatoffer financial assistance or benefits to those citizens whose incomemeets or falls below the poverty line. For example, certain individualsor families may receive food stamps and/or other cash benefits (such asunder the Temporary Assistance for Needy. Families (“TANF”) program) tosupplement their income.

Overall in the United States, the number of individuals and families whoparticipate in these programs is increasing. This increase in the numberof participants in government sponsored benefits programs is creating ahigher caseload, which is not manageable using the legacy systems, whichhave been used to manage benefits. Such systems have also been difficultto upgrade and connect with other systems and new programs because ofthe wide variety of legacy systems, including different programminglanguages, database systems, and operating systems.

In light of the aforementioned problems encountered by existinggovernment sponsored benefits programs there is a need to provide bettermeans for tracking and managing government sponsored cash and non-cashbenefits.

SUMMARY

Methods and systems of the present invention enable needy families andindividuals to more efficiently interact with the various governmentsponsored benefits programs. These methods and systems also permitadministrators, retailers, and other entities involved with theelectronic benefit transfer systems to better manage and use thesystems.

In accordance with the invention, as embodied and broadly described, oneaspect of the invention provides a method for processing governmentsponsored benefits. The method comprises providing a graphical userinterface to a benefit recipient for accessing at least accountinformation concerning at least one benefit type. The method furtherincludes receiving a request from the benefit recipient through thegraphical user interface for displaying the at least account informationconcerning the at least one benefit type. The method also includesdisplaying the at least account information through the graphical userinterface concerning the at least one benefit type.

Another aspect of the present invention provides a method for processinggovernment sponsored benefits. The method includes receiving a requestfrom a benefit recipient through a graphical user interface foraccessing at least account balance information concerning at least onetype of government sponsored benefits. The method further comprisesdisplaying the at least account balance information concerning the atleast one type of government sponsored benefits to the benefit recipientthrough the graphical user interface. Additionally, the method includesreceiving an inquiry from the benefit recipient through the graphicaluser interface concerning the displayed account balance information. Themethod further includes responding to the inquiry from the benefitrecipient concerning the displayed account balance information throughthe graphical user interface.

Yet another method consistent with the present invention is a method formanaging government sponsored benefits. The method includes receiving arequest from at least one retailer through a graphical user interfacefor accessing information regarding transactions handled by the at leastone retailer concerning at least one type of government sponsoredbenefits; and displaying the information regarding the transactionshandled by the at least one retailer concerning the at least one type ofgovernment sponsored benefits at the graphical user interface.

Still another method consistent with the present invention is a methodfor managing government sponsored benefits. The method includesproviding a web browser based administrative terminal to at least onegovernment representative for managing at least one type of governmentsponsored benefits. Further, the method includes creating an account forat least one benefit recipient using the web browser basedadministrative terminal. Also, the method includes issuing a benefitrecipient card to the at least one benefit recipient for the at leastone type of government sponsored benefits.

Additional objects and advantages of the invention will be set forth inpart in the description which follows, and in part will be obvious fromthe description, or may be learned by practice of the invention. Theobjects and advantages of the invention will be realized and attained bymeans of the elements and combinations particularly pointed out in theappended claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments of theinvention and together with the description, serve to explain theprinciples of the invention.

In the drawings:

FIG. 1 is an exemplary benefits processing system environment consistentwith methods and systems of the present invention;

FIG. 2 is a diagram illustrating a benefits processing system consistentwith methods and systems of the present invention;

FIG. 3 is a diagram illustrating various modules of the benefitsprocessing system consistent with methods and systems of the presentinvention;

FIG. 4A is a diagram illustrating an exemplary screen related to accountsetup consistent with methods and systems of the present invention;

FIG. 4B is a diagram illustrating an exemplary screen related to benefitrecipient information management consistent with methods and systems ofthe present invention;

FIG. 4C is a diagram illustrating an exemplary screen related to benefitrecipient search consistent with methods and systems of the presentinvention;

FIG. 4D is a diagram illustrating an exemplary screen displaying benefitrecipient search results consistent with methods and systems of thepresent invention;

FIG. 4E is a diagram illustrating an exemplary screen displaying benefitrecipient information consistent with methods and systems of the presentinvention;

FIG. 5A is a diagram illustrating an exemplary screen related toissuance of a new benefit recipient card consistent with methods andsystems of the present invention;

FIGS. 5B and 5Care diagrams illustrating an exemplary screen related toreplacement of a benefit recipient card consistent with methods andsystems of the present invention;

FIG. 5D is a diagram illustrating an exemplary screen related to. PINchange for a benefit recipient consistent with methods and systems ofthe present invention;

FIG. 6A is a diagram illustrating an exemplary screen related toissuance of a benefit to a benefit recipient consistent with methods andsystems of the present invention;

FIG. 6B is a diagram illustrating an exemplary screen related tocancellation of a benefit consistent with methods and systems of thepresent invention;

FIG. 6C is a diagram illustrating an exemplary screen related toaddition of a benefit program for a benefit recipient consistent withmethods and systems of the present invention;

FIG. 7A is a diagram illustrating an exemplary screen related totransaction history consistent with methods and systems of the presentinvention;

FIG. 7B is a diagram illustrating an exemplary screen related tomessaging for benefit recipients consistent with methods and systems ofthe present invention;

FIG. 7C is a diagram illustrating an exemplary screen related totransaction history by a case number consistent with methods and systemsof the present invention;

FIG. 8 is a schematic diagram illustrating exemplary reports that may begenerated consistent with methods and systems of the present invention;

FIG. 9 is an exemplary display at a point of sale terminal consistentwith methods and systems of the present invention;

FIG. 10 is a flow diagram illustrating an exemplary method forprocessing government sponsored benefits consistent with methods andsystems of the present invention;

FIG. 11 is a flow diagram illustrating another exemplary method forprocessing government sponsored benefits consistent with methods andsystems of the present invention;

FIG. 12 is a flow diagram illustrating an exemplary method for managinggovernment sponsored benefits consistent with methods and systems of thepresent invention;

FIG. 13 is a flow diagram illustrating another exemplary method formanaging government sponsored benefits consistent with methods andsystems of the present invention;

FIG. 14 is a schematic diagram illustrating a redundant arrangement forprocessing government sponsored benefits consistent with methods andsystems of the present invention;

FIG. 15 is a flow diagram illustrating an exemplary method for providinga redundant arrangement for processing government sponsored benefitsconsistent with methods and systems of the present invention; and

FIG. 16 is a flow diagram illustrating an exemplary method for providingaccess to government sponsored benefits consistent with methods andsystems of the present invention.

DESCRIPTION OF THE EMBODIMENTS

One embodiment of this invention, known as EPPIC (“Electronic PaymentProcessing and Information Control”), is presently marketed by ACS State& Local Solutions, Inc. The scope of the present invention, however,encompasses modifications and variations as described by the methods andsystems described herein or as contained within the scope of the listedclaims and their equivalents.

The disclosed benefits processing system is a distributed architecturebased electronic benefits processing system. Accordingly, it may beimplemented using object-oriented programming techniques, such as JAVA,distributed databases, and an Internet browser-based front-end. Severalusers, including federal staff, state staff, county staff, retailers,administrators, and benefit recipients may interact with the benefitsprocessing system without having specialized software on theircomputers. Benefit recipients may communicate with the system usingtelephones and/or point of sale terminals, for example, which may belocated at retailers.

FIG. 1 illustrates an exemplary benefits processing system environment10 consistent with methods and systems of the present invention. Theexemplary benefits processing system environment includes an ElectronicPayment Processing and Information Control (“EPPIC”) system, referred toas a benefits processing system 200, connected via a “Network 1” 110 toa “Benefit Recipient 1” 112, a “Benefit Recipient 2” 114, and a “BenefitRecipient n” 116. Although only three benefit recipients are depicted,any number of benefit recipients may be connected to the benefitsprocessing system. Benefits processing system 100 is further connected,via a “Network 2” to a third party processor 122, a “POS Terminal 1”124, a “POS Terminal 2” 126, and a “POS Terminal n” 128. The benefitsprocessing system is further connected, via a “Network 3” 130 to FederalSystems 132. The benefits processing system may also be connected, via a“Network 4” 140 to a state office 142, which may in turn be connectedvia state network 150 to a “County Office 1” 152, a “County Office 2”154, and a “County Office n” 156. Although only a limited number ofparticipants are depicted in FIG. 1, many more participants, such asretailers, third party processors, federal, state, and county officesmay be connected to the benefits processing system.

Benefit recipients may access benefits processing system'200 throughvarious access methodologies, depending upon the type of transaction.For example, to purchase groceries using food stamps, a benefitrecipient may swipe a benefit recipient card through a point of saleterminal (124 of FIG. 1, for example) located, for example at aretailer, and enter an access code, for example a PIN, to access herfood stamp account. An administrator of the benefit recipient program,which may be a state agent or a County agent (located at a state office142 or at any of the county offices (152, 154, and 156), may thendetermine eligibility of the benefit recipient for the food stampprogram. The eligibility may be used by inputting information concerningthe benefit recipient into benefits processing system 200 and using thatinformation to determine whether certain state/federal thresholds aremet (for example, whether the benefit recipient's income falls below acertain poverty line). And then, assuming eligibility, debit the amountof purchase from the benefit recipient's account for the amount ofpurchase. The administrator may then credit the retailer's account. Theadministrator may also be a third party, for example, a financialinstitution, whom the state and/or the federal government may haveretained for the management of government sponsored benefits, such asfood stamps.

Similarly, a benefit recipient may access cash benefits, such asavailable under the Temporary Assistance for the Needy Families programsusing an ATM machine. Accordingly, the benefit recipient may swipe herbenefit recipient card at the ATM machine (not shown in FIG. 1) and beconnected to the benefits processing system, which then may determinethe eligibility and authenticate the identity of the benefit recipientand grant or deny the cash accordingly. As indicated above a thirdparty, such as a financial institution may act as an intermediary andprovide access to cash benefits to the benefit recipient.

Each of the “Network 1” 110, “Network 2” 120, “Network 3” 130, “Network4” 140, and State Network 150 of FIG. 1 may be any mechanism permittingcommunication among the various components connected by a particularnetwork. Examples of networks that may be used to exchange informationamong the various components of FIG. 1 include networks such as theInternet, telephony networks, private networks, virtual privatenetworks, local area networks, metropolitan area networks, wide areanetworks, ad hoc networks, state networks, frame-relay networks, or anyother mechanism for permitting communication between remote sites,regardless of whether the connection is wired or wireless. Thus, thepresent invention can be used in any environment where information maybe exchanged by any means among the various components, including, forexample the benefits processing system 200, the third party processor122, and the federal system/state offices 132/142.

Using any of the POS terminals (for example, 124, 126, and 128 of FIG.1), a benefit recipient may access food stamp benefits, for example, aspart of a purchase at a retailer.

Federal Systems 132 may include any federal agency involved in thegrant, management, or distribution of benefits. Thus, federal systems132 may include the Federal Reserve Bank, the US Department ofAgriculture, and/or any other federal agency that may be a stakeholderor participant in a benefits program.

State Office 142 may include any state office with a stake in thebenefits program. Using a web-based interface, staff at state office 142may administer the benefits program and/or generate reports.

County office A 152, County office B 154, and County office Z 156 mayprovide county staff with access to the benefits processing system.Although FIG. 1 shows county offices connected to State Office 142 viaState Network 150, which is then connected via “Network 4” 140 tobenefits processing system 200, county offices 152-156 may be connecteddirectly via another network to the benefits processing system.

FIG. 2 is a diagram illustrating a benefits processing system 200,consistent with methods and systems of the present invention. As shownthe benefits processing system may include a computing platform 202, adatabase server 204, and a benefits database 206. Computing platform 202may further comprise applications 210, HTTP server 212, JSP engine 214(described below), POS messaging module 216, and Operating system 218.Although not shown, at least one processor (such as Intel Pentiumprocessor) may execute the various applications to provide functionalityassociated with the benefits processing system. Additionally, HTTPserver 212 may provide automatic file processing ability using, forexample, an Extended Markup Language (“XML”) processor that mayautomatically process files received from a government entity. In oneembodiment, for example, the received file may comply with an XML schemaand relying upon that schema an XML processor may extract recordslocated in the file.

The file may be at least one of a benefit recipient account setup file,a benefit recipient account update file, and a benefit recipient updatefile. By processing any of these files account setup, account update,and benefits update may be handled. Automatic processing of the file mayfurther include acknowledging a receipt of the file, validating a formatof the file; and processing the records located in the file. Thus, forexample, processing of the file may include extracting the relevantinformation from the file and updating databases related to benefitsinformation, such as benefits database 206.

HTTP server 212 may be any HyperText Transport Protocol compatibleserver, such as Apache Web Server, Microsoft IIS, or Netscape EnterpriseServer. Although FIG. 2 depicts a HTTP-based system, one may use anyequivalent system that enables remote devices to access functionalitylocated on the benefits processing system.

JSP Engine 214 may include Java Server Pages-related technology (atechnology from Sun Microsystems) permitting delivery of dynamic contentto the users of benefits processing system 200. In one embodiment, Javalanguage from Sun Microsystems may be used for scripting applications210. JSP Engine 214 may further have access to Sun Microsystem's J2EEplatform for accessing the relevant software libraries/modules. Othersimilar technologies, such as Active Server Pages (from Microsoft) mayalso be used. Additionally, CGI scripts or similar technologies that donot necessarily separate page design from programming logic may also beused.

POS messaging module 216 may provide messaging functionality such as ISO8583 messaging between the POS terminals (not shown in FIG. 2) andbenefits processing system 200. Such messaging may be accomplished overX.25 and IP protocols or other appropriate protocols.

Operating system 218 may provide an interface between the varioussoftware modules of computing platform 202 and hardware associated withthe computing platform. Operating system 218 may be implemented usingSun Microsystem's Solaris operating system. It may also be implementedusing other appropriate operating systems such as UNIX, Linux, MicrosoftNT, HP-UX, AIX, or any other operating system that may interface thesoftware modules with the hardware associated with computing platform202.

Database server 204 may be any database server program, such as Oracle9i from Oracle that may be used to provide access to benefits database206.

Benefits database 206 may be a single database or distributed overmultiple databases. Although FIG. 2 shows only one database, benefitsprocessing system 200 may either include or connect to other databasesas well. Such databases may include, for example, census data or otherrelevant data.

Referring now to FIG. 3, applications 210 may include softwarecomponents providing account management component 250, card managementcomponent 252, benefit management component 254, transaction managementcomponent 256, reconciliation component 258, retailer/third partyprocessor management component 260, report management component 262, anduser management component 264. Of course, the functionality provided inthese modules may be combined or distributed further into sub-modules.Additionally, more functionality may be added using additional softwaremodules.

FIG. 4A shows an exemplary screen related to account setup related toaccount management component (FIG. 3, 250), for example. Accountmanagement component 250 may provide account creation for a benefitrecipient or an authorized representative of the benefit recipient.Thus, for example, as shown in FIG. 4A, an authorized user of benefitsprocessing system 200 may add a new case to an available program, suchas the food stamp program. Accordingly a case worker 402 may add a casewith a certain case number 404, assign it to one of the availableprograms 406, designate a case type 408 and continue 410 withprocessing. Further, as shown in FIG. 4B, the authorized user mayprovide relevant information 412 concerning the new account, which thenmay be stored, for example, in the benefits database of FIG. 2. Also, asdepicted in FIG. 4C, as part of account management component 250, onemay search for benefit recipients using their first or last names, theirsocial security numbers, case numbers, or any other identificationassociated with the benefit recipients (search window 414). FIG. 4Ddepicts the results 416 of such a search. Further, FIG. 4E is anexemplary diagram illustrating at least a portion of information 418relevant to a benefit recipient. This information may include, forexample, the recipient's name, address, gender, date of birth, number ofpeople in the household, and social security number.

Referring back to FIG. 3, card management component 252 may providefunctionality associated with managing benefit recipient cards. Suchcards may be plastic cards with magnetized strips of information, smartcards, or any other card that may be used for retrieval and storage ofbenefits information. Card management component 252 may include, amongother things, issuing new cards, activating the newly issued cards,replacing existing cards (for example damaged or lost cards), changing acard's status, displaying the history of a card (for example, showingall current and prior card numbers with replacement date and status),assigning an authorized representative and/or protective payee to a foodstamp or a cash account, issuing a PIN associated with a particularcard, and allowing benefit recipients to change PIN's, for example,using a POS terminal or an ATM. As shown in FIG. 5A, card managementcomponent 252 may include issuance of a new card 506. Accordingly, acase worker 502 may issue a card to a benefit recipient (recipientinformation 504). Once selected for issuance the benefits processingsystem may require confirmation 508 before issuing the card.Additionally, as depicted in FIGS. 5B and 5C, card management mayfurther include replacement 510 of a lost or damaged card. Also, asshown, in FIG. 5D, using card management one may associate a code with aparticular card, for example a PIN associated with a card.

Referring again to FIG. 3, benefit management component 254 may providefunctionality associated with managing benefits for various benefitrecipients. Benefit management component 254 may include, among otherthings, issuing new benefits, canceling existing benefits, and benefitconversion. Benefits include, but are not limited to, food stampbenefits, cash benefits, and/or any other government sponsored benefits.As shown in FIG. 6A, a user, such as a benefits administrator, mayspecify a particular benefits program, amount of the benefit, and anyother relevant information and issue the benefit to a benefit recipient.Accordingly, as shown in FIG. 6A, case worker information 602 andrecipient information 604 may be displayed. Also, benefit type, benefitamount, and its effective date may be specified (606). Issuance ofbenefits may be confirmed (608). Similarly, the benefits administratormay cancel benefits, as shown in FIG. 6B. Existing benefits may belisted (610). Also, the benefits administrator may add benefitsprograms, as shown in FIG. 6C. As part of the process, the benefitsprocessing system may display a list of available programs to thebenefit recipient, based on, for example, the recipient's eligibilityfor such programs and the programs that the benefit recipient is alreadyassigned to Benefit management may further include conversion of oneform of benefits to either cash or coupons. For example, food stampbenefits may be converted into cash, if approved.

With reference to FIG. 3, transaction management component 256 mayprovide functionality associated with tracking transactions related to aparticular benefit recipient, a particular benefit, or a particularbenefit program. Transaction management component 256 relates to bothclient transactions and retail transactions. Client transactionmanagement may include displaying summary information on every clientdebit/credit transaction and displaying specific detailed informationfor each debit/credit transaction for a client. Retail transactions mayinclude displaying summary information on every transaction for theretailer by the date selected and displaying specifics on any particulartransaction. Thus, for example, as shown in FIG. 7A, an administratormay investigate transaction history 710 of a particular benefitrecipient. Additionally, as shown in FIG. 7B, the administrator may alsosend a message 704 confirming transmittal of transaction history to abenefit recipient: Further, as shown in FIG. 7C, the administrator maydisplay detailed transaction history 706 for a particular benefitrecipient.

Referring now to FIG. 3, reconciliation management 258 may includefunctionality allowing a client to pay back a previous overpayment,adjust balances for a client or a retailer, and provide reconciliationdata related to clients, retailers, and third party processors.

Retailer/third party processor management component 260 may provideretailer search and retailer set up functions. Thus, for example, usingretailer/third party processor management component 260 an administratormay search for a retailer by retailer name or an identification numberassociated with the retailer. Also, the administrator or anotherauthorized user may add new retailers to the system, modify retailerinformation, and/or add new third party processors to the system.

Report management component 262 may provide functionality related togenerating reports, viewing reports, and printing reports. It may alsopermit retrieval of archived data. As shown in FIG. 8, various reportsmay include account activity reports 802, terminal activity reports 804,clearing report 806, database value report 808, administrative reports810, and/or financial reports 812. An account activity report 802 mayreflect all transactions related to an account for a particular day. Itmay also provide information concerning all account related transactionsdone on behalf of a state or an agent of the state. Details may beprovided related to any transaction that impacts an account balance. Atransaction originator may be identified by both a processoridentification number and a batch file name associated with thetransaction. Terminal activity reports 804 may indicate all transactionsthat result in fund movement, for example, to a retailer, third partyprocessor, or an ATM network. Such a report may list the transactiontype, the amount of transaction, the transaction date, the settlementdate, a merchant and terminal identifier, and the benefits impacted byeach transaction. Terminal activity reports 804 may further includesettlement totals for third party processors, retailers, and any otherentity for which funds will be moved. Suspense totals, totals that won'tbe settled until the next processing day, may be reported by individualbenefit types.

Clearing report 806 may provide information concerning total funds thatare being settled Administrative reports 810 includes any other reportsrelated to the administration of benefits. Financial reports 812 mayrelate to the various financial data concerning the benefits, which maybe arranged in any manner.

Referring again to FIG. 3, user management component 264 may includefunctionality related to managing user accounts, for example, adding,modifying, and deleting user accounts. It may also include functionalityrelated to adding, modifying, and deleting login privileges for varioususers of the benefits processing system of FIG. 2.

Referring now to FIG. 9, it shows an exemplary user interface for apoint of sale terminal. The exemplary user interface may include POSterminal identification number 902, the name of the third partyprocessor handling transactions 904, the name of the retailer 906,transaction type 908 (for example, Food Stamp purchase), amount oftransaction 910, a space to enter the benefit recipient's primary accessnumber (PAN), which may be referred as the card number, a pull down listto select a PAN corresponding to the benefit recipient 914, an optionaltrace number 918, and reversal data 920, which may be used to reverse atransaction later.

Referring now to FIG. 10, a flow chart is shown corresponding to anexemplary method for processing government sponsored benefits. As shown,the method may comprise providing a graphical user interface to abenefit recipient for accessing at least account information concerningat least one benefit type (step 1010). The graphical user interface (asreferred to with respect to this method and other methods consistentwith the present invention) may be implemented using a web browser, forexample, Microsoft Internet Explorer, Netscape Navigator, or any othersimilar software. The graphical user interface may be made available ona personal computer, a handheld computer, a television, a thin computer,or any other device capable of accessing a network, such as theInternet, via a graphical user interface. Interactive functionality maybe provided using XML, Java Server Pages, Microsoft Active Server Pagesor any other similar combination of software. For example, FIG. 2depicts a HTTP server 212 and JSP engine 214, which may be used to actas an intermediary between benefits database 206 (of FIG. 2) and thebenefit recipient. Using the graphical user interface, the benefitrecipient may access at least account information concerning at leastone benefit type. The term “account information” as used hereinincludes, but is not limited to, account balance information, and anyother information related to the benefit recipient. Further, benefittype includes at least food stamp benefits and cash benefits.

Next, a request from the benefit recipient through the graphical userinterface may be received for displaying the at least accountinformation concerning the at least one benefit type (step 1020). Thebenefit recipient may request information concerning the at least onebenefit type using any user interface element, such as selecting an itemfrom a pull-down list, clicking a button, or any other type of graphicaluser interface element.

As shown in FIG. 10, the at least account information concerning the atleast one benefit type may then be displayed through the graphical userinterface (step 1030). Consistent with this method, such information maybe displayed immediately after receiving the request or may be displayedat a later time.

Further, the benefits processing system may also display at least oneelectronic message concerning the at least one benefit type to thebenefit recipient (for example, as shown in FIG. 7B).

FIG. 11 depicts a flow chart for another exemplary method for processinggovernment sponsored benefits. The method may include benefitsprocessing system 200 (of FIG. 1) receiving a request from a benefitrecipient through a graphical user interface for accessing at leastaccount balance information concerning at least one type of governmentsponsored benefits (step 1110). As discussed earlier, in one embodimentthe graphical user interface may be a web browser.

Next, the benefits processing system may display the account balanceinformation concerning the at least one type of government sponsoredbenefits to the benefit recipient through the graphical user interface(step 1120).

The benefits processing system may then receive an inquiry from thebenefit recipient through the graphical user interface concerning thedisplayed account balance information (step 1130).

The benefits processing system may then respond to the inquiry from thebenefit recipient concerning the displayed account balance informationthrough the graphical user interface (step 1140). Although this responsemay be generated automatically by the benefits processing system, anoperator may manually respond to the inquiry as well.

Additionally, the benefits processing system may display at least oneelectronic message concerning the inquiry to the benefit recipientthrough the graphical user interface. The at least one electronic mailmessage may be displayed in response to an inquiry from the benefitrecipient. Alternatively, it may be displayed even without any inquiryfrom the benefit recipient. For example, the electronic message mayprovide updated information concerning benefits without being promptedby the benefit recipient.

Referring now to FIG. 12, FIG. 12 shows a flow chart for an exemplarymethod for managing government sponsored benefits: The exemplary methodmay include the benefits processing system receiving a request from atleast one retailer through a graphical user interface for accessinginformation regarding transactions handled by the at least one retailerconcerning at least one type of government sponsored benefits (step1210). Thus, as part of this step, a retailer, such as a grocery storemay access information regarding any transactions that were paid forusing food stamps. In one embodiment, the retailer may access thisinformation using a web browser. The government sponsored benefits maycomprise at least one of food stamp benefits and cash benefits.

The method may further include displaying the information regarding thetransactions handled by the at least one retailer concerning the atleast one type of government sponsored benefits at the graphical userinterface (step 1220). In one embodiment, information regarding thetransactions handled by the at least one retailer may be displayed in asummary form. Additionally, detail information regarding at least onetransaction handled by the at least one retailer concerning the at leastone type of government sponsored benefits may be displayed.

Additionally, at least one retailer may be authorized to handletransactions concerning the at least one type of government sponsoredbenefits.

Further, an administrator or another authorized user may searchinformation concerning the at least one retailer through the graphicaluser interface.

FIG. 13 shows a flow chart for an exemplary method for managinggovernment sponsored benefits. Consistent with the exemplary method, aweb browser based administrator terminal may be provided to at least onegovernment representative for managing at least one type of governmentsponsored benefits (step 1310). The government representative may be afederal, state, or county employee or anyone else authorized to managethe at least one type of government sponsored benefits.

The method may further include creating an account for at least onebenefit recipient using the web browser based administrative terminal(step 1320).

The method may further include issuing a benefit recipient card to theat least one benefit recipient for the at least one type of governmentsponsored benefits (step 1330). The benefit recipient card may besimilar to a credit card, a smart card, or any other type of card and/orapparatus that may be used to access benefits-related information. Thus,for example, as shown in FIG. 5A, a new card may be issued. Similarly,as shown in FIGS. 5B and 5C, using card management component 252 (FIG.3), an authorized user may replace a lost or damaged card. Further, asshown in FIG. 5D, the authorized user may associate a particular code,such as a PIN Code, with a card.

Further, the authorized user, for example, a county employee, may add atleast one benefit program to the at least one type of governmentsponsored benefits. Alternatively, the authorized user may cancel atleast one existing benefit program. Also, the authorized user mayconvert at least one benefit program to another benefit program. Also,as noted earlier, the at least one type of government sponsored benefitsmay be a food stamp benefit or a cash benefit.

As shown in FIG. 2, benefits related information, such as accountinformation may be stored on database server 204. Referring now to FIG.14, an embodiment consistent with the present invention provides atleast one primary server 1402 and at least one secondary server 1404. Inone embodiment, each database transaction is committed to both theprimary server and the secondary server. Also, at least one transactionlog 1406 may be used to track each committed transaction. Although FIG.14 shows only one primary server (or primary database server), onesecondary server, and one log, as many of each may be implemented asneeded consistent with the present invention.

Referring now to FIG. 15, there is shown a method for managinggovernment sponsored benefits using at least one primary server and atleast one secondary server. The method includes providing at least oneprimary server for hosting at least account information concerning anaccount for at least one benefit recipient for at least one type ofgovernment sponsored benefits (step 1510). As used herein the term“hosting” includes, but is not limited to, having a database server forprocessing transactions related to the database server. Additionally,the primary server may be a centralized server or a distributed server.

The method further includes providing at least one secondary server forhosting the at least account information concerning the account for theat least one benefit recipient for the at least one type of governmentsponsored benefits (step 1520).

The method also includes storing information concerning each transactionregarding the account for the at least one benefit recipient for the atleast one type of government sponsored benefits in at least one log(step 1530). The stored information may comprise each transaction, anindex corresponding to each of the transactions, or any other type ofinformation that may be used to update the recovered primary server.

Further, the method includes, upon failure of the at least one primaryserver, providing the at least one secondary server as the primaryserver (step 1540). Failure, as used herein, includes but is not limitedto, a catastrophic failure, a hardware shutdown, a software exception,and/or any problem that may result in either inability or thedegradation of the ability to handle transactions. Also, the secondaryserver may be switched as the primary server automatically or manually.

Next, upon recovery of the at least one primary server, the recovered atleast one primary server is provided as the at least one primary serverand the at least one log may be used to update the recovered at leastone primary server. Updating may include reviewing the log andcommitting the missing transactions to the at least one primary server.

FIG. 16 shows a flow diagram illustrating an exemplary method forproviding access to government sponsored benefits. The exemplary methodmay include receiving information identifying a benefit recipient from aterminal (step 1602). The terminal may be a point of sale terminal, anautomatic teller machine, and/or any other terminal that may be used toreceive information. Further, the terminal may have a device, such as acard reader attached to it. The benefit recipient may swipe a benefitrecipient card thereby providing information coded on, for example, amagnetic strip. Thus, for example, as shown in FIG. 9, among otherthings, information identifying the benefit recipient, for example a PAN914, may be received. Also, consistent with the exemplary method, thebenefit recipient may enter a PIN 916 (FIG. 9) code.

Next, the information identifying the benefit recipient may beauthenticated (step 1604). Authentication may include verifying thebenefit recipient's identity. It may further include determining theeligibility of the benefit recipient to receive a particular benefit.

The exemplary method, as shown in FIG. 16, may further include receivinga request to debit an account corresponding to the benefit recipient(step 1606). This information may be received before authenticating theinformation identifying the benefit recipient. Thus, both theinformation identifying the benefit recipient and the request to debitthe account may be received before authentication.

Further, the exemplary method includes processing the request to debitthe account corresponding to the benefit recipient (step 1608). Thisstep may include debiting the account and recording the transaction forreporting purposes.

Other embodiments of the invention will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. For example, although the variousembodiments have been described by referring to government sponsoredbenefits, they are applicable for benefits sponsored by private entitiesand/or benefits sponsored by a combination of private and public funds.Accordingly, it is intended that the specification and examples beconsidered as exemplary only, with a true scope and spirit of theinvention being indicated by the following claims.

1. A method for processing government sponsored benefits, comprising:providing a graphical user interface to a benefit recipient foraccessing at least account information concerning at least one benefittype; receiving a request from the benefit recipient through thegraphical user interface for displaying the at least account informationconcerning the at least one benefit type; and displaying the at leastaccount information through the graphical user interface concerning theat least one benefit type.
 2. The method of claim 1, wherein thegraphical user interface is a web browser interface.
 3. The method ofclaim 1, wherein the at least account information concerning the atleast one benefit type comprises account balance for the at least onebenefit type.
 4. The method of claim 1, wherein the at least one benefittype comprises at least one of food stamp benefit and cash benefit. 5.The method of claim 1, further comprising: displaying at least oneelectronic message concerning the at least one benefit type to thebenefit recipient.
 6. A system for processing government sponsoredbenefits, comprising: a component for providing a graphical userinterface to a benefit recipient for accessing at least accountinformation concerning at least one benefit type; a component forreceiving a request from the benefit recipient through the graphicaluser interface for displaying the at least account informationconcerning the at least one benefit type; and a component for displayingthe at least account information through the graphical user interfaceconcerning the at least one benefit type.
 7. The system of claim 6,wherein the graphical user interface is a web browser interface.
 8. Thesystem of claim 6, wherein the at least account information concerningthe at least one benefit type comprises account balance for the at leastone benefit type.
 9. The system of claim 6, wherein the at least onebenefit type comprises at least one of food stamp benefit and cashbenefit.
 10. The system of claim 6, further comprising: a component fordisplaying at least one electronic message concerning the at least onebenefit type to the benefit recipient.
 11. A system for processinggovernment sponsored benefits, comprising: means for providing agraphical user interface to a benefit recipient for accessing at leastaccount information concerning at least one benefit type; means forreceiving a request from the benefit recipient through the graphicaluser interface to display the at least account information concerningthe at least one benefit type; and means for displaying the at leastaccount information through the graphical user interface concerning theat least one benefit type.
 12. A computer-readable medium containinginstructions for a method for processing government sponsored benefits,the method comprising: providing a graphical user interface to a benefitrecipient for accessing at least account information concerning at leastone benefit type; receiving a request from the benefit recipient throughthe graphical user interface to display the at least account informationconcerning the at least one benefit type; and displaying the at leastaccount information through the graphical user interface concerning theat least one benefit type.
 13. A method for processing governmentsponsored benefits, comprising: receiving a request from a benefitrecipient through a graphical user interface for accessing at leastaccount balance information concerning at least one type of governmentsponsored benefits; displaying the at least account balance informationconcerning the at least one type of government sponsored benefits to thebenefit recipient through the graphical user interface; receiving aninquiry from the benefit recipient through the graphical user interfaceconcerning the displayed account balance information; and responding tothe inquiry from the benefit recipient concerning the displayed accountbalance information through the graphical user interface.
 14. The methodof claim 13, wherein the graphical user interface is a web browserinterface.
 15. The method of claim 13, wherein the at least one type ofgovernment sponsored benefits comprises at least one of food stampbenefit and cash benefit.
 16. The method of claim 13, furthercomprising: displaying at least one electronic message concerning theinquiry to the benefit recipient through the graphical user interface.17. A system for processing government sponsored benefits, comprising: acomponent for receiving a request from a benefit recipient through agraphical user interface for accessing at least account balanceinformation concerning at least one type of government sponsoredbenefits; a component displaying the at least account balanceinformation concerning the at least one type of government sponsoredbenefits to the benefit recipient through the graphical user interface;a component for receiving an inquiry from the benefit recipient throughthe graphical user interface concerning the displayed account balanceinformation; and a component for responding to the inquiry from thebenefit recipient concerning the displayed account balance informationthrough the graphical user interface.
 18. The system of claim 17,wherein the graphical user interface is a web browser interface.
 19. Thesystem of claim 17, wherein the at least one type of governmentsponsored benefits comprises at least one of food stamp benefit and cashbenefit.
 20. The system of claim 17, further comprising: a component fordisplaying at least one electronic message concerning the inquiry to thebenefit recipient through the graphical user interface.
 21. A system forprocessing government sponsored benefits, comprising: means forreceiving a request from a benefit recipient through a graphical userinterface for accessing at least account balance information concerningat least one type of government sponsored benefits; means for displayingthe at least account balance information concerning the at least onetype of government sponsored benefits to the benefit recipient throughthe graphical user interface; means for receiving an inquiry from thebenefit recipient through the graphical user interface concerning thedisplayed account balance information; and means for responding to theinquiry from the benefit recipient concerning the displayed accountbalance information through the graphical user interface.
 22. Acomputer-readable medium containing instructions for a method forprocessing government sponsored benefits, the method comprising:receiving a request from a benefit recipient through a graphical userinterface for accessing at least account balance information concerningat least one type of government sponsored benefits; displaying the atleast account balance information concerning the at least one type ofgovernment sponsored benefits to the benefit recipient through thegraphical user interface; receiving an inquiry from the benefitrecipient through the graphical user interface concerning the displayedaccount balance information; and responding to the inquiry from thebenefit recipient concerning the displayed account balance informationthrough the graphical user interface. 23-74. (canceled)